Clicking No will allow you to cancel the removal.

Documentation Issues

Some Documented Sample Programs Are Not Available

Some of the program samples listed in the documentation are not yet available. This is a known problem and will be corrected in a later release.

Code Error in "Creating a Control" Topic

The topic, "Creating a Control," contains a code error. In step 4 of the procedure, "To add an event handler," the code to type should be:

edit1.setText("Position = " + HScrollBar.getValue());

Procedure for "Creating a Dynamic HTML Application" Topic has Documentation Error

The topic "Creating a Dynamic HTML Application" contains an error. In step 4 of the procedure, "To view the sample code in your DHTML class," the generated source code begins program execution at the initForm method.

Procedure for "Using the Microsoft Transaction Server (MTS)" Topic has Documentation Error

The topic "Using the Microsoft Transaction Server (MTS)" contains an error. Step 5 of the procedure has been revised and should read, "In the Arguments box, type /p:"MTS Package name", where MTS Package name is the name of the MTS package containing your component. Also, make sure that there are no spaces in this argument."

Development Environment Issues

QuickTips in Text Editor May Cause Unexpected Results

The QuickTips feature in the Text Editor allows you to quickly evaluate any variable or expression by holding the cursor over any code element. This is similar to the behavior of QuickTips in the Visual Basic development environment; however, there is one important distinction. In some cases, QuickTips in the Text Editor will evaluate an entire line of code as if it were an expression, causing the code to execute in order to return a result. For example, holding the cursor over a line containing a Terminate method will cause the method to be executed, in this case terminating the application.

This behavior is by design, but may be unexpected if you are used to the behavior of Visual Basic's QuickTips.

Control Issues

Unlicensed ActiveX Controls Are Not Supported

Unlicensed ActiveX controls are not supported in this Technology Preview version of Visual J++.

Controls Using Windowless Activation Not Supported

Controls using windowless activation are not supported in this Technology Preview of Visual J++.

WFC Controls not Currently Supported as Web Page Content

Problems may occur when a WFC control is placed onto an HTML document. WFC controls cannot yet be hosted directly on HTML documents. This is a known issue and will be addressed in a later release.

Singlethreaded ActiveX Controls Not Supported

Technology Preview 2 of Visual J++ does not fully support singlethreaded ActiveX controls. While the controls may be viewed on the Toolbox, placement of a singlethreaded control onto a form will cause an error dialog box to display and the control will be rejected. This is a known problem and will be corrected in a later release.

Code Development Issues

Templates May Not Display Correctly if Format Settings Are Changed

By default, all templates are formatted with tabs (not spaces). If you want to change the format settings to use spaces instead of tabs, the templates will still have tabs in them. The workaround for this is to load the actual template .java file and then save it using tabs instead of spaces.

Projects Created With Code-Behind HTML Template Will Not Run Correctly on Client Computers if Only Standard Version of Internet Explorer 4.0 or 4.1 is Installed

Projects created with the Code-Behind HTML template will not run correctly on client computers that have only the Standard version of Internet Explorer 4.0 or 4.1 installed. These installations much be updated to include the same version of the Microsoft Vitural Machine for Java and the Windows Foundation Class Libraries that are installed with this product.

Java Files Created in Pre-Build Rules Are Not Built

Java files that are created in pre-build rules will not be built the first time the project is built. An example of this would be a project with a pre-build rule that uses jactivex to create Java wrappers. The first time the build is run, the new Java wrappers will appear in the project, but will not be built. Building a second time will build the new files.

Workarounds for this are:

1. Build the project a second time; now that the new Java files are there, they will build.
2. Create dummy Java files matching the names of the files that will be created in the pre-build rules.

Forms Designer Issues

Copied Controls May Need New Event Handlers

When you copy and paste a control in the Forms Designer, the new copy of the control will, by default, have its events handled by the same handler methods as the original control. To create new handlers for the new control's events, follow these steps:

1. Select the new control in the Forms Designer.
2. In the Properties window, click the Events button to display the event handlers for the control.
3. Highlight each of the handler names in the right column and, once selected, delete them.
4. Add new handlers.

ComFailException May Occur on Forms that Use Data Access

Under some conditions a ComFailException may be thrown on the finalization of a form that uses data access. The work-around is to avoid closing the recordset and connection objects that are used on the form, and instead let the Java VM garbage collection shut the objects down. The connection to the database will still be closed, but the exception should not occur.

Live Control Development

A control in development can be hosted on a form that exists in the same solution as the control. Changes to a control, however, will not be reflected in the hosting form's designer until the control's project is rebuilt, and the designer is closed and reopened.

Sample Issues

Location and Instructions for Using Sample Programs

Please note that Visual J++ samples for Technology Preview 2 are currently only available from the Visual J++ Web site at http://www.microsoft.com/visualj. Please follow the links to download and install the samples. Be sure to revisit our Web site frequently for updates.

Windows Foundation Classes (WFC) Issues

Changes to WFC in Technology Preview 2

As we strive to improve the quality of the Microsoft Windows Foundation Classes between the various Betas, many things have changed that will make code written against Microsoft Visual J++ Technology Preview 1 not compile in Technology Preview 2.

The following is a list of some of the more common things that users will run into:

• The package name for WFC has changed. Instead of being wfc.*, it is now com.ms.wfc.*. For example, Button used to be wfc.ui.Button, it is now com.ms.wfc.ui.Button. The import statement at the top of all your Technology Preview 1 files will need to be changed to reflect this.
• Many properties, methods, and events have changed names. Often, they only need to be renamed, such as changing getAlignText to getTextAlign (typically to be more consistent between controls), but sometimes multiple properties have been merged into one property, or one property is broken into multiple properties. An example of the combining multiple properties would be the "center", "stretch", and "autoSize" properties becoming the "sizeMode" property for the PictureBox control.
• Forms that contain resource files (images and so forth) will not load in Technology Preview 2. To fix this, load the form without it's resource file, and re-add the resources. The new resource file will contain the correct references.
• The constructors for many objects have changed. Most notably, the Font object now has a different set of constructors.
• Control.setStyle is no longer public. The functionality of this method is exposed in other properties.

Solution Packaging and Deployment

Deployment of Server-side Java COM Components in Java Packages

If you implement a COM class in Java, as part of a Java package, and then deploy it as a server component to be called from an ASP page, running the ASP page will fail as the COM server does not get registered. This is because the Microsoft development environment currently does not create the correct directories required for the Java package.

The Java class does not get registered. If you try to register it by hand using VJReg.exe, you get an error back saying "The internal class name "X.Y.Class1' does not match the file or directory name of class file…' and the class cannot be loaded. If you manually create the directory structure corresponding to your Java package under the deployment root directory and then register Class1.class, it registers successfully.

Registration of Java COM Classes Packaged as a DLL Fails